home *** CD-ROM | disk | FTP | other *** search
- Path: EU.net!sun4nl!xs4all!falstaff
- From: falstaff@xs4all.nl (Falstaff)
- Newsgroups: comp.lang.c
- Subject: Re: C coding standards
- Date: 15 Mar 1996 18:25:46 GMT
- Organization: XS4ALL, networking for the masses
- Message-ID: <4iccna$oqi@news.xs4all.nl>
- References: <313B4548.45AA@oc.com> <DnuLzM.8xr@gti-ia.nl> <4i9m00$aqi@infa.central.susx.ac.uk>
- NNTP-Posting-Host: xs1.xs4all.nl
- X-Newsreader: NN version 6.5.0 #666 (NOV)
-
- mattst@cogs.susx.ac.uk (Matthew Stanfield) writes:
-
- >> It suggests that a _guideline_ to function length would be one page long; going on
- >> to say that a page could be 25 lines 60 lines or even 120 lines depending upon wha
- >> you use for display.
-
- Unless the function performs an unavoidable *linear* function, i.e.
- straight-line code, but lots of it, which are used only once.
-
- This tends to give long functions (200 lines or more) and I often feel
- guilty about this, but I write them only if there really is no other way
- around it.
- In these cases, splitting up the function into several smaller ones
- actually makes the code *harder* to understand.
-
- Frank
- --
- The famous GIICM now on line: http://www.xs4all.nl/~falstaff/GIICM.html
- ------------------------------------------------------------------------
- Frank A. Vorstenbosch +31-(70)-355 5241 falstaff@xs4all.nl
-